Systems, methods, and program products for digital pet identification

ABSTRACT

Systems and methods for identifying and tracking pets by use of a pet identification tag or image recognition techniques are disclosed. In exemplary embodiments, a mobile computing device communicates with a pet identification tag over a near-field communication link and a remote server over a wireless communication link. The mobile computing device is configured to identify a pet based on a unique identifier for the tag and/or to provide an image of a pet to the remote server, and to download information about the pet from the remote server using the unique identifier or pet image.

RELATED APPLICATIONS

This application claims priority to and the benefit of U.S. ProvisionalApplication No. 63/045,419, filed Jun. 29, 2020 and entitled SYSTEMS,METHODS, AND PROGRAM PRODUCTS FOR DIGITAL PET IDENTIFICATION, and alsoclaims priority to and the benefit of U.S. Provisional Application No.63/198,457, filed Oct. 20, 2020 and entitled SYSTEMS, METHODS, ANDPROGRAM PRODUCTS FOR DIGITAL PET IDENTIFICATION, the contents of theseapplications being incorporated herein by reference in their entirety.

FIELD

The present invention generally relates to systems and methods forelectronically identifying and tracking a pet, such as a pet dog or cat,or other animals.

BACKGROUND

There is a significant risk that, at some point in a pet's life, thatpet will become lost, missing, or be stolen. According to the AmericanHumane Association, over ten million dogs and cats are lost every yearin the United States alone. Only 23% of these lost pets are everreunited with their owners.

Locating a lost or stolen pet, whether in a large city or in a remoterural location, presents significant technological challenges. Further,if a lost pet is picked up and enters a pet shelter, there is asignificant risk that the pet's owner will never be contacted. Currenttechnology is simply insufficient to enable a pet to be reunited withits owner. The pet will then either be adopted by another party oreuthanized if adoption does not occur after a short while.

To address this crisis, in 2006, Congress passed the PETS Act, whichrequires states and municipalities seeking assistance from the FederalEmergency Management Association (FEMA) to make provisions toaccommodate household pets and service animals in their evacuation plansafter a major disaster or emergency. These accommodations includeenabling the identification of pets and service animals both during andafter an emergency. Accordingly, to comply with the PETS Act, firstresponders need a way to quickly identify an unaccompanied pet.

Historically, pet ID tags have been used to help identify lost pets sothat the pet's owner can be contacted. Pet ID tags have also servedother purposes, such as showing that a pet is licensed. Before theadvent of electronic pet ID tags, engraved metal tags were used for petidentification. These metal tags, however, have a number of drawbacks.Metal tags are capable of providing only limited, and often outdated andinadequate, information about the animal wearing the tag. This is due tothe limited area on which information can be engraved. Indeed, mostmetal tags only have room enough for a pet's name, license number, andone or two telephone numbers. When an owner moves or changes phonenumbers, the information on the metal tag cannot be altered. Rather, thetag needs to be replaced, which can be time consuming. Further, the tagsare primarily made of stainless steel and are prone to folding at theedges, as well as scratching and other wear and tear that causes the tagto become illegible over time. The inadequacy of such tags is made clearin an emergency situation, where accurate information about the pet(such as, for example, ownership and medical information) is critical.

Another pet identification technique has been through the use of chipsinjected below the skin surface of the pet. These chips require a pet tobe transported to a shelter or veterinarian's office in order to implantthe chip and to later scan the chip. However, easy scanning of the chipis not possible if a pet is found, for example, injured on the side ofthe road. Another problem with injected chips is that there are severaldifferent makes and models of chips used domestically and overseas. Mostchip readers can only read one or two types of chips. Therefore, none ofthese injected chips are readable in all locations. Additionally, thedata provided by injected chips is also very limited and potentially outof date.

Early electronic pet ID tags were an attempt to address the shortcomingsof metal and implantable tags. Such early electronic tags, however, onlyprovided a name and phone number associated with a pet, thus lackingmore fulsome records about the pet. More recently, pet industryparticipants, such as PetHub, Inc., have developed and sold pet ID tagsthat help to better identify a pet that wears one, as well as the pet'sowners. Such pet ID tags are capable of being scanned by a smartphoneusing near-field communication (NFC) to obtain an identifier for thetag. The pet ID tags are also affixed with a Quick Response (QR) codethat can be photographed and deciphered by an application running on thesmartphone. These features enable a smartphone or similar device toobtain an identifier associated with the pet that wears the tag. Inturn, the smartphone may use that identifier to obtain additionalinformation about the pet, such as, for example, contact informationassociated with the pet, photographs of the pet and its owner(s), andmedical information. However, conventional pet ID tags have lackedunique identifiers, such as, for example, unique device identifiers.

Relatedly, conventional pet ID tags are not linked to a centralizeddatabase that can be searched independent of whether the party doing thesearching is in possession of the tag. This independent searchingability allows first responders and pet shelters to search for petinformation provided to them independent of the tag. This is useful forreuniting pets with their owners in situations where the tag is notaccessible.

Furthermore, conventional tags that are used as part of a municipal petlicensing program generally include a description of a pet in aproprietary database, which is owned, managed, and maintained by thecity or municipality. Municipal license tags, however, are generally forlocal use only, and the information associated with pets are stored in aclosed database that can only be accessed by those designated animalcontrol authorities. These databases tend to be proprietary, closedsystems, and information contained therein is not publicly available.Hence, if a lost animal wearing a city license is found, the finderneeds to contact municipal authorities to identify the pet, rather thancalling the owner directly. This is a waste of both time and resources.

Further, even municipal animal databases from adjoining localities aregenerally not shared. When two cities or towns share a border betweenthem, animals may wander and cross the border. If the animal is pickedup in the neighboring jurisdiction, that jurisdiction must contact thejurisdiction in which the animal resides.

Furthermore, conventional pet ID tags are not enabled to communicateusing Bluetooth 5.0. Such pet ID tags are unable to provide the expandedcapabilities of Bluetooth 5.0, such as, for example, locate, identify,and track pets within a one-thousand-foot radius while either walking ordriving. Indeed, in an emergency, first responders and animal controlofficers could use Bluetooth 5.0 technology to monitor the petpopulation of an entire area simply by driving through the area, therebyobtaining contact information, pet licensing data, vaccination status,and other pet-related information.

Conventional pet ID tags also tend to consume a lot of power. As such,they cannot sustain multiple years of uninterrupted operation using arelatively small battery. Indeed, current battery technology lacks thepower density to provide a pet ID tag with enough energy to sustainthree years of operating life to the tag.

What is needed are systems and methods whereby pet ID tags can uniquelyidentify and locate a pet wearing the tag and where the pet ID tag isenabled to take advantage of the communication capabilities of Bluetooth5.0. Further, what is needed are pet ID tags that can harvest energysuch that the tag can be used over a long, or potentially unlimited,lifetime without battery replacement.

In addition, what is needed are systems and methods whereby pets can beuniquely identified without requiring the pet to wear a pet ID tag.

SUMMARY

The present invention also addresses these technological problems byproviding new and improved computer systems and methods for uniquelyidentifying a pet by facial, nose print, and/or iris recognition.

Systems and methods in accordance with some exemplary embodiments of thepresent invention electronically identify and track a pet that hasfastened to it a Bluetooth-enabled digital pet identification (ID) tag.The pet ID tag is capable of Bluetooth, or other near fieldcommunication (NFC) with mobile devices, such as, for example,smartphones and laptop computers. The pet ID tag monitors and detectsconditions and events related to the location and environment in whichthe pet wearing the pet ID tag is situated. The pet ID tag alsocommunicates remotely with a central database server that is configuredto store data about the pet to which the pet ID is fastened. The centraldatabase server communicates with an end user of a mobile device toprovide information related to the pet, as well as alert the end user(or other parties, such as pet shelters and law enforcement) ofconditions relating to the pet that warrant intervention.

Systems and methods in accordance with exemplary embodiments of thepresent invention may use, for example, facial recognition technologysuch that a user of a mobile device can take a photograph of a stray petusing the mobile device's camera. The photographic image can becompared, using an application on the mobile device, to images ofregistered pets stored in a central database. If a match is found, thenthe mobile device owner can be provided with associated identifyinginformation regarding the stray pet, such as, for example, otherphotographs of the pet, pet owner information, and medical andbehavioral information for the pet.

Further, systems and methods in accordance with exemplary embodiments ofthe present invention can uniquely identify pets by using nose printrecognition and verification technology. By using such systems andmethods, a user of a mobile device can take a zoomed photograph of thenose of a stray pet using the mobile device's camera. The nose printdiscernable in the zoomed photographic image of the pet's nose can becompared, using an application on the mobile device, to nose printimages of registered pets stored in a central database. If a match isfound, then the mobile device owner can be provided with associatedidentifying information regarding the stray pet, such as, for example,other photographs of the pet, pet owner information, and medical andbehavioral information for the pet.

Further, systems and methods disclosed herein can utilize irisrecognition, or iris biometrics, as an alternative to nose prints touniquely identify stray pets.

Further, the systems, methods, and techniques disclosed herein are notlimited to the identification of stray pets. Although the examplesdisclosed herein are generally applied to lost or stray pets, identicalor similar techniques can be used to identify any animal that can haveaffixed to it a tag, or that possesses features that are uniquelyidentifying, and which can be photographed. Examples of such animalsinclude livestock (such as cattle), service animals (such as carriage orpolice horses), and various athletic team mascots, the identification ofall of which are within the scope of the present invention. The presentinvention addresses this and other technological problems by providingnew and improved computer systems and methods for uniquely identifying apet to which is fastened a pet ID tag that communicates with othercomputer systems using wireless technology, such as, for example, WiFior Bluetooth.

According to an exemplary embodiment of the present invention, a systemfor displaying, on a display operatively connected to a mobile device,information associated with a pet, comprises: (A) one or more databaseshaving stored thereon information comprising: 1) one or more uniqueidentifiers, where each of the one or more unique identifiers isassociated with a corresponding one of one or more wirelesscommunication devices affixed to a corresponding one of one or morepets; 2) pet information related to each of the one or more uniqueidentifiers, the pet information comprising one or more of thefollowing: images of the corresponding pet, contact informationassociated with the corresponding pet, environmental conditionsassociated with the corresponding pet, behavior of the correspondingpet, and medical history of the corresponding pet; (B) one or moreprocessors; and (C) a non-transitory computer readable memoryoperatively connected to the one or more processors and having storedthereon machine-readable instructions that, when executed by the one ormore processors, cause the one or more processors to perform a methodcomprising: receiving, by one of the one or more wireless communicationdevices, via a near-field communication link, a first request from amobile device; and sending, by the one of the one or more wirelesscommunication devices to the mobile computing device, via the near-fieldcommunication link, a first response, the first response comprising theunique identifier associated with the wireless communication device, sothe pet information associated with the unique identifier may beaccessed from the one or more databases for display on the mobilecomputing device.

In an exemplary embodiment the first near-field communication link is aBluetooth communication link.

In an exemplary embodiment the first near-field communication link is aWiFi communication link.

In an exemplary embodiment the first near-field communication link is alink in a mesh communication network.

In an exemplary embodiment each of the one or more wirelesscommunication devices comprise: a housing; an antenna; a wirelesstransceiver operatively connected to the antenna; one or more near-fieldcommunication chips configured to transmit and receive electronic datavia the wireless transceiver; and a non-transitory computer readablememory disposed within the housing.

In an exemplary embodiment each of the one or more wirelesscommunication devices further comprise one or more sensor componentsconfigured to detect status of the wireless communication device.

In an exemplary embodiment the one or more sensor components comprise:an accelerometer configured to measure an acceleration status of thewireless communication device; a global positioning module configured todetermine a geographic location status of the wireless communicationdevice; and a temperature sensor configured to determine an ambienttemperature status of the wireless communication device.

In an exemplary embodiment the detected status is stored in thenon-transitory computer-readable memory of the corresponding one or morewireless communication devices.

In an exemplary embodiment the one or more wireless communicationdevices further comprise: a battery configured to provide power to thewireless communication device; and a lighting element configured toilluminate the wireless communication device.

In an exemplary embodiment the system further comprises a remote server.

In an exemplary embodiment the method further comprises: receiving, bythe one of the one or more wireless communication devices, from theremote server, a second request; and sending, in response to the secondrequest, from the one of the one or more wireless communicationsdevices, to the remote server, the detected status of the one of the oneor more wireless communication devices, for storage in the one or moredatabases as associated with the corresponding unique identifier of theone of the one or more wireless communication devices.

A method according to an exemplary embodiment of the present inventioncomprises the steps of establishing, by the mobile computing device, afirst near-field communication link with a wireless communicationdevice, wherein the wireless communication device is affixed to the pet;sending, by the mobile computing device, via the first near-fieldcommunication link, a first request to the wireless communicationdevice; receiving, by the mobile computing device from the wirelesscommunication device, via the near-field communication link, a firstresponse, the first response comprising an identifier that uniquelyidentifies the wireless communication device; sending, by the mobilecomputing device, via a second wireless communication link, a secondrequest to a remote server, the second request including the identifier;receiving, by the mobile computing device via the second wirelesscommunication connection, a plurality of information associated with theidentifier; and displaying, by the mobile computing device on thedisplay operatively connected thereto, the plurality of informationassociated with the identifier.

In accordance with exemplary embodiments, a computer-implemented methodof displaying, on a display operatively connected to a mobile computingdevice, information associated with a pet, comprises the steps ofcapturing, by the mobile computing device, an image imprinted on asurface of a wireless communication device, wherein the wirelesscommunication device is affixed to the pet; processing, by the mobilecomputing device, the captured image to obtain an identifier thatuniquely identifies the wireless communication device; sending, by themobile computing device, via a first wireless communication link, afirst request to a remote server, the first request including theidentifier; receiving, by the mobile computing device via the firstwireless communication connection, a plurality of information associatedwith the identifier; and displaying, by the mobile computing device onthe display operatively connected thereto, the plurality of informationassociated with the identifier.

In accordance with exemplary embodiments, a computer-implemented methodof storing information associated with a pet, comprises the steps ofestablishing, by the mobile computing device, a first near-fieldcommunication link with a wireless communication device, wherein thewireless communication device is affixed to the pet; sending, by themobile computing device, via the first near-field communication link, afirst request to the wireless communication device; receiving, by themobile computing device from the wireless communication device, via thenear-field communication link, a first response, the first responsecomprising an identifier that uniquely identifies the wirelesscommunication device; associating, by the mobile computing device, aplurality of text and images with the identifier; sending, by the mobilecomputing device, via a second wireless communication link, a secondrequest to a remote server, the second request including the identifier,the plurality of text and images, and an instruction to cause the remoteserver to store the identifier and the plurality of text and images in aremote database; and receiving, by the mobile computing device via thesecond wireless communication connection, a confirmation message fromthe remote server that the identifier and the plurality of text andimages have been stored.

In accordance with exemplary embodiments, a wireless communicationdevice comprises; a housing; an antenna; a wireless transceiveroperatively connected to the antenna; a processor; and, operativelyconnected to the processor, a memory; one or more near-fieldcommunication chips configured to transmit electronic messages via thewireless transceiver; an accelerometer configured to measure anacceleration of the wireless communication device; a global positioningmodule configured to determine a geographic location of the wirelesscommunication device; a temperature sensor configured to determine anambient temperature of the wireless communication device; a batteryconfigured to provide power to the wireless communication device; and alighting element configured to illuminate the wireless communicationdevice.

In accordance with exemplary embodiments, a wireless communicationdevice comprises an individually identifiable near-field communication(NFC) and/or QR-coded pet ID tag. In embodiments, the pet ID tag isBluetooth 5.0-enabled. In embodiments, the pet ID tag is configured witha data-based operating system accessible by a URL and is activated byeither tapping, scanning, photographing, or utilizing Bluetoothactivation. In embodiments, the pet ID tag communicates with a mobilecommunication device that executes an application that displays detailedpet profile pages (with identifying photographs). The mobilecommunication device provides for one-click dialing to a pet owner'sphone to provide immediate and direct contact with the owner. Inembodiments, the pet ID tag notifies a pet owner notification wheneverthe pet ID tag is activated. In embodiments, the pet ID tag isconfigured to display full color (RGB) LED light and to generate a fullspectrum of colors and blinking patterns. In embodiments, the pet ID tagcan be configured to act as a virtual fence creating a radius of up to800 feet from an owner's mobile communication device or home. Inembodiments, the pet ID tag can be accessed or “pinged” to disclose itscurrent location. In embodiments, the pet ID tag can be configured as anode in a mesh network in order to expand its communication range.According to embodiments, the pet ID tag includes an embeddedaccelerometer that performs activity monitoring, battery management,bark detection, and the like. According to embodiments, the pet ID tagincludes an embedded temperature sensor that is configured to providealerts if an ambient temperature is too hot or too cold. In embodiments,the pet ID tag includes low-energy components and management system, anda battery having an average 2-year lifespan. In embodiments, the pet IDtag includes self-charging and energy harvesting components thatregenerate energy produced by solar, vibrations, movement, or body heat.In embodiments, the pet ID tag has logging capabilities, and sendslocation, temperature daily activity, and other data to a remote server.According to embodiments, the remote server employs artificialintelligence and predictive analytics to data collected for training andpersonalized uses. According to embodiments, the remote server providesautomated email and/or text message reminders for license renewals,rabies booster shots, veterinarian appointments, and other scheduledevents. According to embodiments, the pet ID tag and remote serverprovides for the sending of lost pet alerts that notifies entities inclose proximity to the tag, such as, for example, pet shelters locatedwithin a 20 mile radius, that a pet is lost or in distress. Inembodiments, the pet ID tag and remote server provide for a “return toowner” feature that allows for an unlimited number of people (such asfriends, neighbors, family, and veterinarians) who are pre-authorized totake custody of a pet if the pet owner is unavailable.

In accordance with exemplary embodiments, a computer-implemented methodof transmitting, to a user device, information associated with a pet,comprises the steps of associating each one of a plurality of pet imageswith associated pet information; storing the pet images and associatedpet images in a database; receiving a first pet image from a userdevice; retrieving one or more of the plurality of pet images from thedatabase; processing the received first image and the one or moreretrieved pet images with image recognition software; identifying as amatching pet image one of the one or more retrieved pet images thatmatches the received first pet image; retrieving from the database thepet data associated with the matching pet image; and transmitting theretrieved pet data to the user device

DESCRIPTION OF THE DRAWINGS

Exemplary embodiments of the present invention will be described withreferences to the accompanying figures, wherein:

FIG. 1 illustrates an exemplary pet identification system in accordancewith exemplary embodiments of the present invention;

FIG. 2 illustrates an exemplary pet ID tag and mobile communicationdevice that can be used in accordance with exemplary embodiments of thepresent invention.

FIG. 3 illustrates two views of an exemplary pet ID tag used inaccordance with exemplary embodiments of the present invention;

FIG. 4 illustrates electrical diagrams of exemplary pet ID tags inaccordance with exemplary embodiments of the present invention;

FIG. 5 is a flow diagram showing a process for a mobile communicationdevice to communicate with a pet ID tag and obtain informationassociated with a pet wearing the tag, in accordance with exemplaryembodiments of the present invention;

FIG. 6 is a flow diagram showing a process for a mobile communicationdevice to communicate with a pet ID tag and to remotely storeinformation associated with a pet wearing the tag, in accordance withexemplary embodiments of the present invention;

FIG. 7 is a flow diagram showing a process for a pet ID tag to detectand record one or more conditions associated with the tag, in accordancewith exemplary embodiments of the present invention;

FIG. 8 is a flow diagram showing a process for a mobile communicationdevice to receive alerts associated with one or more conditionsassociated with a pet ID tag, in accordance with exemplary embodimentsof the present invention;

FIG. 9 illustrates an exemplary pet identification system that makes useof facial recognition technology, in accordance with exemplaryembodiments of the present invention;

FIG. 10 illustrates an exemplary pet identification system that makesuse of nose print recognition technology, in accordance with exemplaryembodiments of the present invention;

FIG. 11 is a flow diagram showing a process for a mobile communicationdevice to communicate with a remote server to obtain informationassociated with a facial image of a stray pet, in accordance withexemplary embodiments of the present invention;

FIG. 12 is a flow diagram showing a process for a mobile communicationdevice to communicate with a remote server to obtain informationassociated with a nose print image of a stray pet, in accordance withexemplary embodiments of the present invention;

FIG. 13 is a flowchart illustrating a pet facial recognition algorithmaccording to an exemplary embodiment of the present invention;

FIG. 14 is a flowchart illustrating a nose print recognition algorithmaccording to an exemplary embodiment of the present invention;

FIG. 15 is a representative diagram of a pet tagging system according toan exemplary embodiment of the present invention; and

FIG. 16 illustrates an exemplary pet identification system in accordancewith exemplary embodiments of the present invention.

DETAILED DESCRIPTION

In exemplary embodiments, the present invention addresses technologicalbarriers to pet identification and tracking by providing a technologicalsolution in the form of a computer system and process that utilizes amobile computing device, a pet ID tag, and a remote server.

In exemplary embodiments, the pet ID tag monitors the location,activity, and ambient conditions of a pet that wears the tag andcommunicates related information to the remote server for futureretrieval by a mobile computing device. The pet ID tag may be configuredto be scanned, tapped, and/or photographed by a mobile computing device,which captures data from the scanning, tapping, or photographing. Themobile computing device processes the captured data to uniquely identifythe tag and, by extension, the pet wearing the tag. The mobile computingdevice is capable of wireless communication with the pet ID tag, wherethe wireless communication may be near field communication (such asBluetooth 5.0) or WiFi. The mobile computing device is also capable ofremote communication with the remote server to download informationassociated with the scanned pet ID tag from the server and/or to uploadinformation associated with the scanned pet ID tag to the remote server.

In exemplary embodiments, the present invention seeks to address thetechnological problem of electronically identifying and tracking petsthrough the use of an identification tag. Conventional pet ID tags arenot equipped with a unique identifier that may be scanned and/orphotographed. A unique identifier for the pet ID tag allows the tag tobe associated with information that is unique to the pet that wears thetag. This enables a mobile computing device (such as a smartphone) thatscans or taps the tag, or photographs a QR code on the tag, to quicklydetermine the tag's unique identity. Once the unique identity of the tagis determined, the mobile computing device can request to downloadand/or upload information from or to a remote server, where theinformation uniquely pertains to the wearer of the tag, such as, forexample, photographs of the pet, dietary restrictions, and medicalinformation, to name a few. The pet ID tag is also configured tocommunicate with the remote server to report monitored conditions, suchas the geographic location of the pet ID tag, ambient temperature,whether the tag has been scanned, and activity information in connectionwith the wearer of the tag such as, for example, how many steps thewearer of the tag has taken during a time interval.

In exemplary embodiments, the present invention also preferably utilizesBluetooth 5.0, which include greater speed and improved range ascompared to prior Bluetooth versions. For example, Bluetooth 5.0 hasfour times the range, two times the speed, and eight times thebroadcasting message capacity of older versions of Bluetooth. Indeed,Bluetooth 5.0-enabled devices can use data transfer speeds of up to 2Mbps, which is double what prior versions support. A Bluetooth5.0-enabled pet ID tag can also communicate over distances of up to 800feet (or 240 meters), which is four times the 200 feet (or 60 meters)possible with earlier versions of Bluetooth. The present inventiontherefore addresses and solves technological barriers to the efficientidentification of pets that have become separated from their owners.

FIG. 1 is a block diagram that illustrates a system, generallydesignated by reference number 100, in accordance with an exemplaryembodiment of the present invention. The system 100 includes a mobilecomputing device 101, a pet ID tag 110, and a remote server 100.

Mobile computing device 101 can be a smartphone, a tablet computer, alaptop computer or other type of mobile computing device. Mobilecomputing device is equipped with a processor (not shown) that executesoperating system and application program instructions and controls thephysical hardware of the device. Mobile computing device 101 is equippedwith a display 102, which can be, in embodiments, a touchscreen. Display102 is configured to display a plurality of application programs(“apps”) that include instructions stored on memory that, when executedby the processor, cause the processor to carry out operations related tothe app. In this regard, mobile computing device 101 displays graphicaluser interfaces associated with a camera app 104 and a pet ID app 105. Auser of mobile computing device 101 interacts with display 102 tooperate camera app 104 and pet ID app 105 through the correspondinggraphical user interfaces.

Camera app 104 is used to control camera 103, which may be an includedfeature of mobile device 101. In embodiments, camera 103 is a standardhigh- or low-resolution smartphone-integrated camera. Camera app 104enables an end user of mobile device 101 to take high- or low-resolutionphotographs.

Pet ID app 105 is an application program that an end user interacts withthrough display 102. In embodiments, pet ID app 105 is a network-enabledapplication that communicates over a near field communication link, suchas link 150, or over a remote communication link, such as link 160. Tocommunicate over links 150 and 160, pet ID app 105 may access, throughan appropriate application program interface (API), wireless networkadapter 106 of mobile computing device 101. Communication over link 150is typically near field communication (NFC), such as, for example,Bluetooth 5.0 or earlier versions of Bluetooth. Alternatively,communication link 150 can, in some embodiments, be a WiFi link, wheremobile computing device 101 and pet ID tag 110 connect to the same WiFinetwork. Further, link 150 can, in embodiments, be a link in a meshcommunication network (or meshnet) where several devices and routers areconnected directly to one another. In such embodiments, pet ID tag 110can communicate over an extended range greater than 800 feet, and can belocated either indoors or outdoors. Thus, in embodiments, pet ID tag 110can communicate with mobile devices carried by first responders within ahome to enable quick location of a pet. Further, when communicating overa mesh network, pet ID tag 110 can communicate with other Bluetoothenabled pet ID tags within communication range. Communication over link160, on the other hand, is typically over a cellular or WiFi connectionto a wide area network, such as the Internet.

In exemplary embodiments, pet ID app 105 is an application program thatis configured to provide an end user with the capability of determiningthe identity and associated information of a pet wearing a pet ID tag.Pet ID app 105 is configured to process information received from a petID tag, such as pet ID tag 110 depicted in FIG. 1. Pet ID app 105receives data over a near field communication link, such as link 150,and processes that data to determine a unique identifier for the tag.According to embodiments, Pet ID app 105 extracts the unique identifierfrom a data stream received from the tag. Pet ID app 105 associates theunique identifier with data associated with a pet, such as medical dataor photographs of the pet. Pet ID app 105 can be used by an end user tocommunicate, via link 160, to a remote server (such as remote server130) to upload the data to remote server 130. Further, pet ID app 105may be configured to create a data request, either automatically or asinitiated by a user, that includes the unique identifier received frompet ID tag 110 and send the request over link 160 to remote server 130.Pet ID app 105 may be further configured to receive a response to thedata request and display information received from remote server 130. Inembodiments, pet ID app 105 may communicate over line 160 using aUniform Resource Locater (URL) for remote server 130.

For example, in embodiments, pet ID app 105 sends a data request thatincludes a unique identifier for pet ID tag 110, along with requestdata, such as, for example, a request for a corresponding pet's latestphotographs, the pet's medical records, and the pet's owner's contactinformation. Pet ID app 105 then receives this data in a response fromremote server 130 and displays the photographs and medical and ownerdata on display 102 of mobile computing device 101. Alternatively, petID app 105 can send a data request to remote server 130 for all datacorresponding to the unique tag identifier. In response, pet ID app 105would receive all data corresponding to the pet associated with the tag(e.g., photographs, medical records, owner contact information, locationdata for the tag, temperature of the location of the tag, activityinformation for the tag wearer, and other data). Pet ID app 105 can thenmakes this data available for display on display 102.

Furthermore, in exemplary embodiments, pet ID app 105 is configured toreceive alert information from remote server 105. Examples of alertinformation may include times and locations that pet ID tag 110 wasscanned, tapped, or photographed. This provides an indication of where apet is located when mobile computing device 101 is out of range forBluetooth or other near field communication. Another example of an alertis the ambient temperature of the environment in which the tag issituated. Such a feature serves to alert an end user of mobile computingdevice 101 whether the pet wearing the tag is located in a place ofexcessive heat or cold, such as, for example, a locked automobile insummer or tied up outdoors in winter. Another example of an alert is onewhich alerts the end user of pet ID app 105 of unusual activity (or longperiods of inactivity) by the wearer of the tag. Such an alert caninform the end user that a pet is in distress or is unwell. Pet ID app105 can also receive an alert that the pet ID tag 110 has been removedfrom the pet wearing it, or that the battery of the tag is low. Manyother types of alerts are possible and within the scope of the presentinvention. According to exemplary embodiments, alerts are received asmessages on link 160 between remote server 130 and mobile computingdevice 101. Alerts may be expressed as electronic messages, such astexts or emails, sent to the user through the mobile computing device101, as audio alerts played through speakers (now shown) of the mobilecomputing device 101 and/or as vibration or other motion alertsactivated on the mobile computing device 101.

In exemplary embodiments, once pet ID app 105 receives an alert, the appcan provide an alert signal on mobile computing device 101, such as, forexample, an alarm or beep. Pet ID app 105 may then display informationcorresponding to the alert, such as a map of the location of the tag orlocal temperature and weather conditions at the tag's location.

As referred to above, system 100 also includes pet ID tag 110. Accordingto exemplary embodiments, pet ID tag 110 is an electronic device that isconfigured to be fastened or affixed to a pet, such as a dog or cat. Asshown in FIG. 1, pet ID tag 110 includes a housing 120. In exemplaryembodiments, housing 120 is made from carbon fiber material, built to amilitary grade standard. As such, exemplary embodiments of housing 120are completely waterproof. In one or more embodiments, housing 120 iscomposed of a durable and lightweight plastic material that is resistantto scratching, etching, and similar wear and tear, and which maintainsits shape over time. In embodiments, housing 120 has a physical diameterof less than 32 millimeters.

Pet ID tag 110 includes a processor 111. Processor 111 is the centralprocessing unit of the tag, which is configured to execute operatingsystem and application program instructions and is the centralcontroller for the tag. In embodiments, processor 111 can be amicrocontroller capable of being embedded for use in wearable devices,such as, for example, the PIC family of microcontrollers manufactured byMicrochip Technology, Inc., the MCS family of microcontrollersmanufactured by Intel Corp., or the LPC family of microcontrollersmanufactured by NXP Semiconductors N.V.

Pet ID tag 110 also includes random access memory (RAM) 112, which is,in exemplary embodiments, an on-board memory module. RAM 112 can beeither dynamic random access memory (DRAM) or static random accessmemory (SRAM), as those terms are understood by those skilled in theart. RAM 112 is configured to store operating system, device driver, andapplication program instructions, as well as associated data buffers.RAM 112 is operatively connected to processor 111 such that processor111 can fetch data and instructions for execution and store results.

As shown in FIG. 1, pet ID tag 110 also includes a Bluetooth chip 113.According to exemplary embodiments, Bluetooth chip 113 is a module thatis capable of communicating over a Bluetooth communication link. Inembodiments, Bluetooth chip 113 is configured to support Bluetooth 5.0or earlier versions of Bluetooth. Bluetooth chip 113 may, alternatively,support other communication protocols that provide for near fieldcommunication (e.g., communication at a distance of 800 feet or less)with a similarly enabled device. As shown, Bluetooth chip 113communicates over a near field communication link, such as link 150, viaa wireless transceiver 123, which is operatively connected to antenna119. In embodiments where link 150 is a WiFi link, then pet ID tag 110includes a WiFi network adapter or wireless transceiver (not shown)which enables communication over WiFi. In embodiments, antenna 119 canbe a ceramic antenna. In embodiments, Bluetooth chip 113 is an ultra-lowpower integrated circuit.

In embodiments, Bluetooth chip 113 can be configured to communicate withsmart home security devices, such as security cameras and alarm systems.In addition, Bluetooth chip 113 can be configured to communicate withanother Bluetooth chip of a nearby pet wearing another pet ID tag. Suchcommunication can, in embodiments, facilitate contact tracing, wherebyit may become important to track which animals a potentially infectedanimal has come into contact with.

In some embodiments, where WiFi rather than Bluetooth communication isused, pet ID tag 110 includes a wireless transceiver that is adapted tocommunicate over a WiFi network. In such embodiments, the WiFitransceiver may take the place of Bluetooth chip 113 and is configuredto communicate with devices external to pet ID tag 110.

Pet ID tag 110 also includes NFC chip 114. In embodiments, NFC chip 114is separated from Bluetooth chip 113, and provides a pet ID tag 110 witha unique identifier. This unique identifier can be referred to as aunique serial number. NFC chip 114 is operatively connected to wirelesstransceiver 123, which itself is operatively connected to antenna 119,and thereby communicates over line 150. NFC chip 114 is configured to bescanned by a nearby device, such as mobile computing device 101. Inembodiments, mobile computing device 101 sends a signal over link 150 toantenna 119. The signal is detected by wireless transceiver 123, whichrelays the signal to NFC chip 114, which then, itself, sends a signalover line 150 to mobile computing device 101. The signal sent by NFCchip 114 includes, in exemplary embodiments, the unique identifier ofpet ID tag 110.

Referring back to FIG. 1, pet ID tag 110 also includes temperaturesensor 115. In exemplary embodiments, temperature sensor 115 isoperatively connected to processor 111. Temperature sensor 115 isconfigured to monitor the ambient temperature of pet ID tag 110. Inexemplary embodiments, temperature sensor 115 provides periodic updatesof the ambient temperature to processor 111. In other exemplaryembodiments, temperature sensor 115 provides the ambient temperatureonly when the temperature changes by a predefined amount. Processor 111receives the temperature updates and, in some exemplary embodiments,executes a program that transmits, via wireless transceiver 123 andantenna 119, the ambient temperature via a cellular or WiFi link (suchas link 170) to a remote server, such as remote server 130. As will beexplained, this enables remote server 130 to provide warnings to mobiledevice 101 or other third parties regarding dangerous temperatureconditions.

According to embodiments, temperature sensor 115 may be a thermocouplemade from, for example, nickel chromium/constantan, iron/constantan,nickel chromium/aluminum, nicrosil/nisil, copper/constantan, and/orplatinum rhodium. Alternatively, in embodiments, temperature sensor 115may be a resistance temperature detector (RTD) made from platinum orother appropriate conductors. In embodiments, temperature sensor 115 maybe a thermistor made from a polymer or ceramic material. In embodiments,temperature sensor 115 may be a semiconductor based integrated circuit(IC) that senses the temperature of the ambient air around it. Inembodiments, temperature sensor 115 may also detect the body temperatureof the animal wearing pet ID tag 110, thereby enabling remote diagnosisof a medical condition of the pet.

Pet ID tag 110 also includes accelerometer 116. Accelerometer 116 isconfigured to measure acceleration of pet ID tag 110. For example, asthe pet wearing pet ID tag 110 runs or jumps, accelerometer 116 willdetect a change in the pet's acceleration. Accelerometer 116 is alsooperatively connected to processor 111. As such, accelerometer 116provides periodic updates of the pet's acceleration (i.e., the pet'sactivity) to processor 111. Accelerometer 116 can also detect, forexample, in the case of dogs, whether the pet is barking excessively.Further, accelerometer 116 can also, in some exemplary embodiments,provide processor 111 with a pet's lack of activity. For example,accelerometer 116 may detect that pet ID tag 110 has not had anyactivity (i.e., acceleration) over a predetermined time period andreport this condition to processor 111. Processor 111, in turn, executesa program that transmits, via wireless transceiver 123 and antenna 119,the activity information received from accelerometer 116 via a cellularor WiFi link (such as link 170) to a remote server, such as remoteserver 130. As will be explained, this enables remote server 130 toprovide warnings to mobile device 101 or other third parties regardingunusual activity (or absence of activity) of the pet wearing the tag.Further, in embodiments, processor 111 may accumulate and store activitydata based on monitoring accelerometer 116. Such activity data may bestored on the tag itself, for example, in RAM 112.

In embodiments, accelerometer 116 may be a board mounted embeddedaccelerometer configured for an acceleration range of from ±20 g to±6000 g. In embodiments, accelerometer 116 may be piezoelectricaccelerometer. Alternatively, accelerometer 116 can be a MEMSaccelerometer.

As shown in FIG. 1, pet ID tag 110 also includes battery 117. Accordingto exemplary embodiments, battery 117 provides electrical power to petID tag 110. Battery 117 may be operatively connected to processor 111.In some embodiments, battery 117 also includes an associated batterymonitor. In these exemplary embodiments, battery 117 is able to monitorpower levels and determine whether the power level has fallen below apredetermined threshold. In these exemplary embodiments, the associatedbattery monitor provides a warning signal to processor 111, indicatingeither the current power level or the amount of time the battery hasbefore it will be completely drained and/or has reached a critical levelof power. Processor 111, in exemplary embodiments, may execute a programthat transmits, via wireless transceiver 123 and antenna 119, thebattery information via a cellular or WiFi link (such as link 170) to aremote server, such as remote server 130. As will be explained, thisenables remote server 130 to provide warnings to mobile device 101 orother third parties regarding the condition of battery 117. Inembodiments, battery 117 is a long life battery, capable of powering petID tag 110 for three years or more.

In embodiments, battery 117 may work in tandem with an energy harvestingmechanism (not depicted) that is capable of being included with pet IDtag 110. Such an energy harvesting mechanism can include photovoltaic(solar) cells, vibration/motion harvesting, or RF energy harvesting. Inembodiments, the selection of an energy harvesting mechanism can bebased, at least in part, on a determination of how much energy pet IDtag 110 will require over its lifetime.

In embodiments, in addition to communicating with remote server 130 overa cellular or WiFi link, pet ID tag 110, via processor 111, wirelesstransceiver 123, and antenna 119, may communicate over these links witha central emergency response service in order to directly alert thoseservices of a dangerous condition relating to the pet wearing the tag.

In exemplary embodiments, pet ID tag 110 also includes QR pictogram 118.QR pictogram 118 is, in exemplary embodiments, a machine-readable matrixbarcode that is printed or affixed to housing 120 of pet ID tag 110. Assuch, QR pictogram 118 can be photographed by a camera, such as camera103 on mobile computing device 101. QR pictogram 118 has encoded thereina unique identifier for pet ID tag 110. According to exemplaryembodiments, this unique identifier matches or is associated with theunique identifier provided by NFC chip 114. Typically, an end user ofmobile computing device 101 can photograph QR code 118, using camera103. Mobile computing device 101 has stored thereon software that isconfigured to analyze the digital image of QR code 118 and decipher theunique identifier of pet ID tag 110.

FIG. 1 also shows that pet ID tag 110 includes light emitting diode(LED) 121. In exemplary embodiments, LED 121 is a lighting element thatis configured to generate a spectrum of colors, which enables pet ID tag110 to convey different alert information based on the color. LED 121 isoperatively connected to processor 111. According to exemplaryembodiments, processor 111 may determine the time of day from aninternal clock (not shown). Based on the determined time of day,processor 111 may be configured to cause LED 121 to generate a colorthat is easily detected at that time. For example, processor 111 maycause LED 121 to generate a bright magenta color at night. Further,processor 111 may cause LED 121 to flash or display a certain sequenceof colors based on other data, such as ambient temperature, activity ofthe pet wearing the tag, and remaining battery life. Further, inembodiments, processor 111 can be configured to cause LED 121 to blinkaccording to one or more patterns in order to attract attention to thewearer of the tag.

FIG. 1 also shows that pet ID 110 may include a global positioningsystem (GPS) 122. GPS 122 may determine geographic coordinates at whichpet ID tag 110 is located. GPS 122 is operatively connected to processor111 and provides geographic coordinates to the processor so that thelocation of pet ID tag 110 can be tracked. In embodiments, GPS 122 canbe configured for radio frequency identification (RFID) using amicrochip or transistor, and which is operatively coupled to wirelesstransceiver 123 to send and receive signals. GPS 122 may also, inembodiments, be configured for radio tracking and/or GPS and satellitetracking. Further, in embodiments, processor 111 may accumulate andstore location data based on monitoring of GPS 122. Such location datamay be stored on the tag itself, for example, in RAM 112.

In embodiments, pet ID tag 110 can include other sensors, such as, forexample, a separate sensor to monitor the temperature of the pet, aglucose monitor that monitors blood glucose levels, and an oxygenmonitor that monitors the level of oxygen in the blood of the pet. Inembodiments, pet ID tag 110 can also include two-way voice communicationcapabilities as well as high frequency speakers, which enable directcommunication with the pet. The use of monitors for temperature andother health-oriented data associated with a pet can be used in aprocess to automatically record this data with a central server, such asremote server 130, described below.

As shown in FIG. 1, system 100 also includes remote server 130. Inexemplary embodiments, remote server 130 can be a desktop computer, alaptop computer, a tablet, a smartphone, or any server quality computer.Remote server 130 is configured to communicate over a wide area or localarea network. As shown, remote server 130 communicates over remote links160 and 170. Link 160 is a communication link between remote server 130and mobile computing device 101. Link 170 is a communication linkbetween remote server 130 and pet ID tag 110. In embodiments, remoteserver 130 is configured to receive and respond to requests from mobilecomputing device 101. For example, mobile computing device 101 may senda request to create an account for a pet ID tag 110. In such a case,remote server 130 receives a unique identifier for pet ID tag 110, aswell as associated data, such as photographs of the pet, owner contactinformation, and medical data associated with the pet. Remote server 130creates the account in database 140, which is operatively coupled toremote server 130. Database 140 associates the unique identifier for petID tag 110 with the associated information. In exemplary embodiments,database 140 may be, for example, a relational database, a hierarchicaldatabase, or a structured text file. In embodiments, database 140 is acentralized, globally accessible database that is public andnon-proprietary. That is, database 140 may be configured to be queriedseparately from a device other than mobile device 101. For example, inembodiments, database 140 can be configured to be accessed, updated, andqueried through a web interface that is accessible to the public or toanimal control authorities. In some embodiments, database 140 isconfigured to be deployed in a cloud computing environment and to bemaintained as a separate entity from the manufacturer of pet ID tag 110.Thus, in situations where the tag manufacturer experiences aninterruption of its business activities, the information in database 140would be preserved. In embodiments, database 140 is independentaccessible nationwide or worldwide using, for example, a mobileapplication used by emergency response or law enforcement personnel,enabling quick and efficient identification and rescue of lost pets.Database 140, in some embodiments, can be accessed through a secure webinterface. Further, in embodiments, link 160 and link 170 may becommunication links over the Internet. As such, communication withremote server 130 over links 160 and 170 can be established,respectively, by pet ID app 105 and pet ID tag 110 using a URL thatidentifies remote server 130.

Remote server 130 can receive from mobile computing device 101 a requestto update information related to a pet. In embodiments, mobile computingdevice sends an update request to remote server 130 via link 160. Anupdate request can be a request to update information relating to thepet, such as, for example, a change in owner contact information orupdated photographs.

In exemplary embodiments, remote server 130 can receive health-orienteddata from a pet ID tag, such as, for example, the pet's temperature,blood pressure, glucose level, and other health variables. Remote server130, in embodiments, can include software that correlates these healthvariables with known disease parameters and, as a result, determine andstore a preliminary diagnosis for the pet. For example, if a pet ispresenting symptoms of the novel coronavirus (COVID-19) based uponhealth monitor readings taken by pet ID tag 110, then the health datacorresponding to those symptoms can be transmitted to remote server 130,whereby remote server 130 can determine a COVID-19 diagnosis andassociate this diagnosis with the pet. Further, when an animal's healthreadings return to normal, remote server 130 can receive health datathat reflects the animal's improved condition, thereby altering thediagnosis to indicate the animal is presently healthy.

Further, remote server 130 can be configured to receive an indication ofwhether a pet ID tag has come within a predetermined proximity, forexample, six feet, of another pet ID tag. For example, a pet ID tag 110can detect when it is within six feet or less of another pet ID tag.When this occurs, pet ID tag 110 transmits, to remote server 130 overlink 160, the identifier of its own pet ID tag and the identifier of theother, closely encountered pet ID tag. Remote server 130, inembodiments, can be configured to associate and track the pet ID tagsthat have come in close proximity to one another. If any of those pet IDtag identifiers is associated with a pet that has had a diagnosis of acontagious diseases (such as COVID-19), then the information associatedwith the pet ID tag is then updated as being a potential contact of theinfected animal. This information can be periodically reviewed by petcontrol or health authorities in developing a contact tracing system forpets which would ultimately help community health. Authorities couldanalyze the contact data and contact the owners of all pets who havebeen determined to have come into contact with an infected animal. Inembodiments, remote server 130 can be configured to automatically notifypet owners about potential infection of their pets because of closecontact with a known infected animal.

Remote server 130 can also receive a request for information from mobilecomputing device 101. A request for information can include a uniqueidentifier for a pet ID tag 110. In this case, remote server 130accesses database 140 using the unique identifier as a key. Remoteserver 130 retrieves the information associated with the uniqueidentifier and transmits this information (such as photographs, medicalinformation, and owner contact information) to mobile computing device101 for display on display 102.

Remote server 130 may be configured to receive information from pet IDtag 110 via link 170, as shown in FIG. 1. In embodiments, pet ID tag 110transmits to remote server 130 data, such as ambient temperature,activity data, location data, whether the tag has been scanned, tapped,or photographed, and/or remaining battery life. Pet ID tag 110 alsotransmits its unique identifier (stored in NFC chip 114) so that remoteserver 130 can identify the tag from which the data is coming from.Remote server 130 receives this data and, in exemplary embodiments,stores the data in database 140. In exemplary embodiments, remote server130 is configured to determine whether the received data from pet ID tag110 warrants sending an alert to mobile computing device 101 or to otherthird parties. Other third parties can include, without limitation,nearby pet shelters and law enforcement.

For example, remote server 130 may receive information that the ambienttemperature of pet ID tag 110 exceeds 90° F., which might be determinedto be unsafe for a pet. Remote server 130 may also receive locationinformation from pet ID tag 110, providing the tag's geographiccoordinates. Since these conditions may indicate that the pet is lockedin a closed vehicle, remote server 110 may then send an alert messagevia link 160 to the pet's owner, who may be in possession of mobilecomputing device 101. Further, remote server 130 may send an alert withthe tag's geographic coordinates to law enforcement, which enables lawenforcement to respond and provide assistance to the pet. Other alertscenarios relating to location, activity, and battery conditions arepossible and within the scope of the present invention. In exemplaryembodiments, the alert sent by the remote server 130 may request aresponse within a predetermined time period (e.g., a certain number ofseconds or minutes) to confirm that the alert was received or that someaction will be taken in response to the alert. Further, in exemplaryembodiments, if a response is not received within the predetermined timeperiod, the remote server 130 may send the alert to a third party, suchas a third party designated by the pet owner, so that prompt action maybe taken in response to the alert.

FIG. 2 illustrates a system, generally designated by reference number200, that includes an exemplary pet ID tag 210 and mobile communicationdevice 201 that can be used in accordance with exemplary embodiments ofthe present invention. As shown, mobile computing device 201 includes anexemplary pet identification application with a graphical user interfacethat includes functionality to access the location of pets that arewearing a pet ID tag. Further, mobile computing device 201 is configuredto receive alerts and to manage lost alerts, which may have beentransmitted while the device was turned off. The pet identificationapplication running on mobile computing device 201 also allows an enduser to add new pets, thereby providing the ability to manage multiplepet ID tags.

As shown, system 200 also includes a pet ID tag 210 having a frontportion 210 a and a back portion 210 b. The back portion 210 b includesa QR code, which has encoded the tag serial number. In exemplaryembodiments, the tag serial number provides the unique identifier forthe tag. The front portion 210 a may be customizable by the pet owner todisplay information, such as, for example, the name of the pet, contactinformation, and a website associated with the pet ID tag.

FIG. 3 illustrates two views of a printed circuit board (PCB),designated by reference number 310, of a pet ID tag in accordance withexemplary embodiments of the present invention. The various modulesdepicted as enclosed within pet ID tag 110 in FIG. 1 are mounted on PCB310. PCB 310 includes a top layer 310 a and a bottom layer 310 b. Thevarious modules of the pet ID tag as described herein may beinterconnected via the circuit board 310, and provide the functionalitydescribed in connection with pet ID tag 110 in FIG. 1.

As shown, top layer 310 a of PCB 310 provides PCB 310 with immunity fromelectromagnetic interference by utilizing stitching to tie togethercopper from the top and bottom layers. Top layer 310 a has configuredthereon coin cell contacts and debug pads. Bottom layer 310 b, as shown,includes Bluetooth circuitry, a ceramic antenna, and an on-boardaccelerometer.

FIG. 4 illustrates electrical diagrams of exemplary pet ID tags inaccordance with exemplary embodiments of the present invention. FIG. 4Adepicts a PCB top layer layout and placement 410 a for a pet ID tag,according to an embodiment, where overall two distinct layers are usedfor the PCB. FIG. 4B also depicts a PCB bottom layer and placement 410b, which corresponds to top layer 410 a. Further, FIG. 4C depicts athree-dimensional board view 410 c, which corresponds to top layer 410a. Finally, FIG. 4D shows another three-dimensional board view 410 d,which illustrates a coin cell connection.

FIG. 5 is a flow diagram showing a method 500 for a mobile communicationdevice to communicate with a pet ID tag and obtain informationassociated with a pet wearing the tag, in accordance with exemplaryembodiments of the present invention. In exemplary embodiments, method500 is carried out by a mobile computing device, such as mobilecomputing device 101 depicted in FIG. 1.

Method 500 begins at step 501. At step 501, mobile computing device 101establishes an NFC session with pet ID tag 110. In exemplaryembodiments, mobile computing device 101 pairs with pet ID tag 110 overa near field communication link, which, in exemplary embodiments, is nogreater than 800 feet in distance. In exemplary embodiments, the sessionbetween the devices is established using Bluetooth, such as Bluetooth5.0.

Next, at step 503, mobile computing device 101 transmits a first requestto pet ID tag 110 over the established NFC session. The first requestmay include an identification request, whereby mobile computing devicerequests a unique identifier for pet ID tag 110. In exemplaryembodiments, pet ID tag 110 receives the identification request andaccesses NFC chip 114 to provide the unique identifier.

At step 505, mobile computing device 101 receives a unique identifierfor pet ID tag 110 via the NFC session. According to exemplaryembodiments, the unique identifier can be a serial number that isencoded and stored within NFC chip 114 of pet ID tag 110. In otherexemplary embodiments, mobile computing device 101 can receive theunique identifier by photographing and deciphering the identifier from aQR pictogram printed on pet ID tag 110. In this case, method 500 wouldnot require the establishment of an NFC session between mobile computingdevice 101 and pet ID tag 110.

At step 507, mobile computing device 101 sends a second requestincluding the unique identifier of pet ID tag 110 to remote server 130.In exemplary embodiments, mobile computing device 101 sends the secondrequest over a WiFi or cellular data link via the Internet, as describedin connection with link 160 in FIG. 1. Remote server 130 is configuredto receive the request and to retrieve text and image data associatedwith the unique identifier of pet ID tag 110. According to exemplaryembodiments, the second request need not include a password to requesttext and image data associated with the unique identifier of the tag.Alternatively, the remote server 130 may require input of a passwordbefore information can be provided to the mobile computing device 101.In this regard, a user may make a specific request for informationthrough an application program, such as pet ID app 105.

Next, at step 509, mobile computing device 101 receives text and imagesassociated with the unique identifier pet ID tag 110 from remote server130. In exemplary embodiments, the text and images can include, forexample, pet photographs, medical data pertaining to a pet, and owneridentification information. Mobile computing device 101 receives theinformation from remote server 130 via link 160.

Finally, at step 511, mobile computing device 101 displays the receivedtext and images on a display device. In exemplary embodiments, mobilecomputing device 101 invokes an application program, such as pet ID app105 in FIG. 1, which displays the information on display 102. Inembodiments, the text and information displayed on display 102 includescontact information for the owner of the pet wearing pet ID tag 110. Insuch embodiments, mobile computing device displays the contactinformation in a manner whereby an end user can click or touch thecontact information in order to place a call to one or more owners ofthe pet. Moreover, in embodiments, mobile computing device can receive(at step 509) multiple contacts corresponding to the pet wearing pet IDtag 110, such as friends, family members, and medical personnel. In suchembodiments, at step 511, mobile computing device 101 displays a list ofcontacts corresponding to the pet. Each contact can be displayed sothat, when the displayed contact is clicked or touched by an end user ofmobile computing device 101, a call is automatically placed to theselected contact.

FIG. 6 is a flow diagram showing a method 600 for a mobile communicationdevice to communicate with a pet ID tag and to remotely storeinformation associated with a pet wearing the tag, in accordance withexemplary embodiments of the present invention. In exemplaryembodiments, method 600 is carried out by a mobile computing device,such as mobile computing device 101 depicted in FIG. 1.

Method 600 begins at step 601. At step 601, mobile computing device 101establishes an NFC session with pet ID tag 110. In exemplaryembodiments, mobile computing device 101 pairs with pet ID tag 110 overa near field communication link, which, in exemplary embodiments, is nogreater than 800 feet in distance. In exemplary embodiments, the sessionbetween the devices is established using Bluetooth, such as Bluetooth5.0.

Next, at step 603, mobile computing device 101 transmits a first requestto pet ID tag 110 over the established NFC session. The first requestmay include an identification request, whereby mobile computing devicerequests a unique identifier for pet ID tag 110. In exemplaryembodiments, pet ID tag 110 receives the identification request andaccesses NFC chip 114 to provide the unique identifier.

At step 605, mobile computing device 101 receives a unique identifierfor pet ID tag 110 via the NFC session. According to exemplaryembodiments, the unique identifier includes a serial number that isencoded and stored within NFC chip 114 of pet ID tag 110. In otherexemplary embodiments, mobile computing device 101 can receive theunique identifier by photographing and deciphering the identifier from aQR pictogram printed on pet ID tag 110. In this case, method 600 wouldnot require the establishment of an NFC session between mobile computingdevice 101 and pet ID tag 110.

Next, at step 607, mobile computing device 101 associates images and/ortext information with the received unique identifier for pet ID tab 110.In exemplary embodiments, mobile computing device 101 may executecomputer readable instructions that generate a second request, where thesecond request includes the unique identifier and data fields that storeor point to text and image data. The text and images may correspond to apet wearing pet ID tag 110. Such data may include updated photographs ofa pet, updated owner contact information, or medical data for the pet,such as, for example, a vaccination schedule. In exemplary embodiments,a user may input updated information associated with the uniqueidentifier through an application program, such as pet ID app 105.

Once the text and image data has been associated with the uniqueidentifier, method 600 proceeds to step 609. At step 609, mobilecomputing device 101 sends a third request to remote server 130.According to exemplary embodiments, the third request includesinstructions to store the unique identifier for pet ID tag 110 alongwith the associated text and image data. Upon receipt of the thirdrequest, remote server 130 may store the received unique identifier andassociated text and image data in a database, such as database 140. Asshown in FIG. 1, mobile computing device 101 may send the third requestover the Internet via a WiFi or cellular data link such as link 160.

At step 611, mobile computing device 101 receives a confirmation fromremote server 130 that the unique identifier and associated image andtext information has been stored. In exemplary embodiments, mobilecomputing device 101 receives the confirmation over link 160.

FIG. 7 is a flow diagram showing a method 700 for a pet ID tag to detectand record one or more conditions associated with the tag, in accordancewith exemplary embodiments of the present invention. In exemplaryembodiments, method 700 is carried out by a processor of a pet ID tag,such as pet ID tag 110 depicted in FIG. 1, executing computer readableinstructions.

Method 700 begins at step 701. At step 701, pet ID tag 110, viaprocessor 111, monitors for several conditions, either concurrently orserially. For example, as shown in FIG. 7, pet ID tag 110 monitors aglobal positioning device, such as GPS 122. In exemplary embodiments,pet ID tag 110 monitors GPS 122 to determine whether the location of petID tag 110 is greater than a predetermined distance away from a homebase or some other location, thus aiding in determining whether a pethas strayed from home or from some other location. In embodiments, petID tag 110 is configured to store a perimeter radius surrounding apredetermined geographic coordinate location. In such cases, processor111 utilizes GPS 122 to determine if pet ID tag 110's current locationis beyond the perimeter radius. In this way, pet ID tag 110 provides fora virtual fence around any predetermined geographic coordinate.

Also shown in FIG. 7, pet ID tag 110 monitors a temperature sensor, suchas temperature sensor 115. In embodiments, pet ID tag 110 monitorstemperature sensor 115 to determine whether the ambient temperature ofthe tag exceeds or falls below a threshold value. This aids indetermining whether the pet wearing the tag is, for example, locked in ahot enclosed vehicle or being restrained outside in winter.

Further, pet ID tag 110 may monitor an on-board battery, such as battery117 in FIG. 1. In embodiments, pet ID tag 110 may monitor battery 117 todetermine the amount of charge left in the battery and how much moretime it will take for the battery to drain.

In addition, as shown in FIG. 7, pet ID tag 110 may also monitor anaccelerometer, such as accelerometer 116 in FIG. 1. In embodiments, petID tag 110 may monitor accelerometer 116 to determine the accelerationsand movements of the pet wearing the tag. Pet ID tag 110 may determinewhether activity, or a lack of activity, shown by the accelerometer isunusual. For example, if a pet is known to be housed in a smallapartment, pet ID tag 110 may determine that excessive running and/orjumping is unusual for such an environment. By contrast, if a pet isnormally very active, pet ID tag 110 may determine that very littlerecent activity is unusual and may indicate illness of the pet.

Pet ID tag 110 may also monitor an on-board Bluetooth chip, such asBluetooth chip 113 depicted in FIG. 1. In exemplary embodiments, pet IDtag 110, via processor 111, may monitor Bluetooth chip 113 to determinewhether the pet ID tag 110 has been scanned by a mobile computingdevice. This information can be used to further determine whether a pethas been interacting with strangers. Further, pet ID tag 110, viaprocessor 111, may monitor whether it has come into physical proximitywith another pet ID tag, which, as described above, can be important indeveloping contact tracing for interactions with infected animals.

Next, at step 703, pet ID tag 110 detects one or more conditions basedupon the monitoring performed in step 701. As noted above, pet ID tag110 may determine that an ambient temperature of the tag exceeds orfalls below certain temperature thresholds. Or, as another example, petID tag 110 may determine that the global position of the tag indicatesthat the pet wearing the tag has strayed from home.

Next, at step 705, pet ID tag 110 associates a unique identifier for thetag with the one or more detected conditions. In exemplary embodiments,pet ID tag 110 retrieves a unique tag identifier, or serial number, fromNFC chip 116. This unique identifier is associated in memory (e.g., RAM112) with the one or more detected conditions in preparation forgenerating an electronic message to send to a remote server.

At step 707, pet ID tag 110 generates an electronic message thatincludes the unique tag identifier and the one or more detectedconditions. In exemplary embodiments, the electronic message isconstructed as one or more data records or packets that logicallyassociate the unique identifier for the tag with data that correspondsto or describes the detected conditions. For example, if the uniqueidentifier for a tag is denoted by the numerical sequence 1111, then petID tag 110 generates an electronic message that associates the numericalsequence 1111 with data that describes conditions detected at step 703.For example, if pet ID tag 110 detects an ambient temperature of greaterthan 90° F., then the generated electronic message would associate thenumber 1111 with an appropriate message, such as “temperature too high,”along with the temperature detected. It should be noted that there arenumerous ways the electronic message can be generated to associate theunique identifier with the detected condition information which arewithin the scope of the present invention.

Lastly, at step 709, pet ID tag 110 transmits the generated electronicmessage to a remote server, such as remote server 130, for storage in aremote database, such as database 140. In exemplary embodiments pet IDtag 110 transmits the message over a WiFi or cellular link, such as link170 in FIG. 1. Upon receipt of the message, remote server 130 stores theunique tag identifier, along with the detected condition information, indatabase 140. Remote server 130 may then transmit an alert to one ormore mobile devices, or to one or more public authorities, whichdescribes the detected condition.

It should also be noted that, in embodiments, remote server 130 can alsoperform certain predictive analytics related to the received conditioninformation. In embodiments, remote server 130 processes the conditioninformation to predict future behavioral results for the pet wearing petID tag 110. For example, remote server 130 may correlate pet activitywith time of day, location, and ambient temperature in order assistowners in determining optimal strategies to achieve desired petbehavior.

In some embodiments, pet ID tag 110 may also transmit a message, via aBluetooth or other near field communication link, to a smart homesecurity system (not shown). Such a smart home security system can thennotify a homeowner of a potentially dangerous condition. For example,pet ID tag 110, via processor 111, may detect excessive barking orunusual activity from monitoring accelerometer 116. In such a case, petID tag 110 may transmit a message via Bluetooth link from via wirelesstransceiver 123 and antenna 119 to a home security system to alert thehomeowner of the condition.

In some embodiments, pet ID tag 110 may transmit a message to remoteserver 130 that reflects a mode of communication by the animal wearingthe tag. For example, when a dog senses a stranger or unfamiliar animalroaming near the owner's property, the dog will bark or move in acertain pattern. Sensors (such as accelerometer 116, GPS 122, and/ortemperature sensor 115) can detect changes that correspond to excessivebarking or anxious movements by the pet and send that data to remoteserver 130.

Further, in embodiments, remote server 130 may be configured to runartificial intelligence or machine learning algorithms to learn, overtime, a pet's individual habits based on the data received from pet IDtag 110. For example, remote server 130 may be configured to learn thata certain pattern of movement (acceleration), location, and temperaturedetected by pet ID tag 110 corresponds to a situation in which the petis alarmed. In such a case, remote server 130 can be configured tocommunicate with a home alarm system over a network communication path(such as the Internet of Things), instructing the home alarm system toperform preventive activities, such as, for example, turning lights onand off, or emitting loud alarm or vocal sounds.

After step 709, method 700 returns to step 701, where pet ID tag 110returns to monitoring for various conditions, as described above.

FIG. 8 is a flow diagram of a method 800 for a mobile communicationdevice to receive alerts associated with one or more conditionsassociated with a pet ID tag, in accordance with exemplary embodimentsof the present invention. Method 800 is carried out, in exemplaryembodiments, by a mobile computing device, such as mobile computingdevice 101 depicted in FIG. 1.

Method 800 begins at step 801. At step 801, mobile computing device 101monitors a network link, such as link 160, for alerts that indicateconditions relating to a pet ID tag, such as pet ID tag 110. At step803, mobile computing device 101 receives one or more alerts over link160 from remote server 130. In exemplary embodiments, the receivedalerts indicate that a particular pet ID tag, such as pet ID tag 110,has associated with it one or more dangerous conditions. For example,the alerts may indicate that the ambient temperature of the tag iseither above or below a predetermined temperature threshold. Further,the alerts may indicate that the pet ID tag's location is more than apredetermined distance away from a home base location.

In addition to alerts pertaining to potentially dangerous conditions,alerts may also be received to remind a pet owner of certain tasks anddeadlines. For example, an alert can be received which reminds a petowner that it is time to take the pet for a check-up at a veterinarian.Further, an alert can be received which reminds the pet owner to reorderor administer certain medications to the pet. In addition, an alert canbe received which informs the pet owner that his or her pet has comeinto close physical proximity with an animal that has been diagnosed(either automatically due to saved health data, or by a veterinarian)with one or more contagious diseases.

At step 805, mobile computing device 101 may generate one or moreelectronic notification messages based on the received alerts. At step807, mobile computing device 101 may send the one or more electronicnotification messages to a plurality of recipients. For example, ifmobile computing device 101 receives an alert that indicates that a petis lost, then, at step 807, the mobile computing device may sendelectronic notification messages to one or more law enforcementrecipients, or to one or more animal shelters that are close to thepet's last known location. These electronic notifications provideinstructions to these public authorities to be on the lookout for a lostpet. According to embodiments, notifications can be sent by mobilecomputing device 101 to recipients that members of the First ResponderNetwork Authority (FirstNet). As another example, if mobile computingdevice 101 receives an alert indicating that the ambient temperature ofpet ID tag 110 exceeds a threshold (indicating, for example, that thepet is trapped in a locked car), then the device may send an electronicnotification to law enforcement, providing the geographic coordinates ofthe tag. This enables law enforcement to quickly locate and rescue thepet. Further, in embodiments, if pet ID tag 110 is scanned or tapped bya mobile device (such as another smartphone), mobile computing device101 may receive location information that indicates the current locationof the pet wearing the tag.

At step 809, mobile computing device 101 may display one or more of thereceived alert messages on a display device, such as display 102depicted in FIG. 1. According to exemplary embodiments, the alertmessage can indicate a dangerous condition associated with the petwearing a pet ID tag 110. Alternatively, the alert can be a reminder ofan upcoming medical appointment for the pet.

Pets may communicate with their owners (and others) in many ways. Inthis regard, in various exemplary embodiments, artificial intelligenceand predictive analytics may be applied to the pet ID tag and associatedsystems and methods to help interpret these non-verbal signals. Inexemplary embodiments, the inventive Bluetooth enabled smart-tags mayhave onboard data processing capabilities, and transfer data over thecellular network without any human interaction. This data may beutilized to help personalize each user's experience. Predictiveanalytics and artificial intelligence may be applied to obtain thedesired behavioral results.

FIG. 9 is a block diagram that illustrates a system, generallydesignated by reference number 900, in accordance with an exemplaryembodiment of the present invention. The system 900 includes a mobilecomputing device 901 and a remote server 930 operatively coupled to adatabase 940.

As with mobile device 101 of FIG. 1, mobile device 901 includes adisplay 902, a camera 903, and a camera app 904. These componentsprovide similar functionality as corresponding components 102, 103, and104, respectively, described above in connection with FIG. 1. Further,mobile device 901 also executes Pet ID app 905.

As with Pet ID app 105 of FIG. 1, Pet ID app 905 is an applicationprogram that an end user interacts with through display 902. Inembodiments, pet ID app 905 includes all the functionality described inconnection with pet ID app 105.

In exemplary embodiments, pet ID app 905 is an application program thatis configured to provide an end user with the capability of determiningthe identity and associated information of a pet based on a photographof the pet. Pet ID app 905 is configured to access an image database onmobile device 901, such as image database 907. As shown, an end user mayuse camera app 904 to take a photograph, using camera 903, of a straypet, such as the pet 950 depicted in FIG. 9. Once a photograph of pet950 is taken, the image of the pet can be stored locally in imagedatabase 907 via camera app 904.

Pet ID app 905 can be used by an end user to communicate, via link 960,to a remote server (such as remote server 930) to obtain informationrelating to the pet in a stored photograph. Pet ID app 905 is configuredto transmit, via wireless network adapter 906, one or more petphotographs over link 960, along with an associated data requestrelating to the pets in the transmitted photographs. Further, Pet ID app905 is configured to receive a response to the data request and displayinformation received from remote server 930. In embodiments, like pet IDapp 105 in FIG. 1, pet ID app 905 may communicate over line 960 using aUniform Resource Locater (URL) for remote server 930.

As shown in FIG. 9, system 900 also includes remote server 930. Inexemplary embodiments, remote server 930 can be a desktop computer, alaptop computer, a tablet, a smartphone, or any server quality computer.Remote server 930 is configured to communicate over a wide area or localarea network. As shown, remote server 930 communicates over link 960.Link 960 is a communication link between remote server 930 and mobilecomputing device 901. In embodiments, remote server 930 is configured toreceive and respond to requests from mobile computing device 901. Asshown in FIG. 9, remote server 930 is operatively connected to database940. According to exemplary embodiments, database 940 associates digitalphotographs of pets with corresponding information. In exemplaryembodiments, database 940 may be a relational database, a hierarchicaldatabase, or a structured text file. In embodiments, database 940 is acentralized, globally accessible database that is public andnon-proprietary. That is, database 940 may be configured to be queriedseparately from a device other than mobile device 901. For example, inembodiments, database 940 can be configured to be accessed, updated, andqueried through a web interface that is accessible to the public and/orto animal control authorities. In some embodiments, database 940 isconfigured to be deployed in a cloud computing environment. Inembodiments, database 940 is independently accessible nationwide orworldwide using, for example, a mobile application used by emergencyresponse and/or law enforcement personnel, enabling quick and efficientidentification and rescue of lost pets. Database 940, in someembodiments, can be accessed through a secure web interface. Further, inembodiments, link 960 may be a communication link over the Internet. Assuch, communication with remote server 930 over link 960 can beestablished by pet ID app 905 using a URL that identifies remote server930.

According to exemplary embodiments, remote server 930 can receive arequest for information from mobile computing device 901. A request forinformation can include a digital photograph of a stray pet. Uponreceipt of the request and digital photograph, remote server 930 invokesfacial recognition module 935. Facial recognition module 935 is asoftware module executed by remote server 930. Facial recognition module935 is configured to read in a digital photograph and select facialfeatures of the photograph in accordance with techniques known in theart. After analyzing and selecting facial features, facial recognitionmodule 935 accesses database 940. Database 940 stores facial images ofpreviously registered pets and associates those images with informationcorresponding to the pet depicted in the image. Facial recognitionmodule 935 compares features in the received photograph with features inimages stored in database 940. If there is a match between the facialimage in the received photograph and the image in the database, thenremote server 930 retrieves information associated with the image andtransmits this information (such as other photographs, medicalinformation, and owner contact information) to mobile computing device901 for display on display 902.

In exemplary embodiments, the facial recognition module 935 may employfacial recognition algorithms such as, for example, principal componentanalysis using eigenfaces, linear discriminant analysis, elastic bunchgraph matching using the Fisherface algorithm, the hidden Markov model,the multilinear subspace learning using tensor representation, theneuronal motivated dynamic link matching and combinations thereof, toname a few.

FIG. 13 is a flowchart illustrating a pet facial recognition algorithm,generally designated by reference number 1300, according to an exemplaryembodiment of the present invention. The process 1300 includes a facedetection step 1301, a face alignment step 1303, a feature extractionstep 1305 and a face recognition step 1307. The face detection step 1301may involve location of one or more pet faces in a received image orvideo and marking the located pet faces with a bounding box. The facedetection step 1301 may invoke face detection methods such as, forexample, feature-based detection and image-based detection using deeplearning, to name a few. The output of the face detection step 1301 mayinclude face location, face size, and/or face pose, to name a few. Theface alignment step 1303 may include normalization of detected face orfaces to be consistent with images in the database 940, such as geometryand photometrics. The feature extraction step 1305 involves extractionof features from the face or faces to produce a feature vector that canbe used for the recognition task. The face recognition step 1307includes matching of the face against one or more known faces in aprepared database, such as the database 940. The matching algorithm mayseek an exact match and/or may seek an image that is similar to theinput image. In exemplary embodiments, the face recognition step 1307may generate a new face that is similar to the input face for inclusionin the database 940. This may be particularly useful if no match isfound, either exact or similar, in case the pet of interest is foundagain at a later point in time.

Further, in embodiments, remote server 930 may be configured to runartificial intelligence or machine learning algorithms to learn, overtime, whether a facial image and/or iris image corresponds to a lost petwithout requiring the comparison of the facial image or iris image to aregistered image. For example, remote server 930 may be configured tolearn that a certain facial expression is more common for lost pets thanfor pets that have not strayed. For example, remote server 930 may, inembodiments, learn that pets that have strayed from their owners andhomes have a certain “distressed” expression, which indicates that thepet is either lost, sick, or otherwise having difficulty. In suchembodiments, remote server 930 may generate an alert to pet controlauthorities to call for assistance to help reunite the pet with itsowner, or to provide aid. Such an alert would include the receivedfacial image of the distressed pet.

FIG. 10 is a block diagram that illustrates a system, generallydesignated by reference number 1000, in accordance with an exemplaryembodiment of the present invention. The system 1000 includes a mobilecomputing device 901 and a remote server 1030 operatively coupled to adatabase 1040.

According to exemplary embodiments, mobile device 901 is functionallyequivalent to the mobile device depicted in FIG. 9, which includes adisplay 902, a camera 903, and a camera app 904. As mentionedpreviously, these components provide similar functionality ascorresponding components 102, 103, and 104, respectively, describedabove in connection with FIG. 1. Further, mobile device 901 alsoexecutes Pet ID app 905.

Further, as explained above, Pet ID app 905 is an application programthat an end user interacts with through display 902. In embodiments, PetID app 905 includes all the functionality described in connection withPet ID app 105.

As explained in connection with FIG. 9, according to exemplaryembodiments, pet ID app 905 is an application program that is configuredto provide an end user with the capability of determining the identityand associated information of a pet based on a photograph of the pet.Specifically, Pet ID app 905 is configured to access an image databaseon mobile device 901, such as image database 907. As shown, an end usermay use camera app 904 to take a zoomed photograph, using camera 903, ofthe nose of a stray pet, such as the pet 950 depicted in FIG. 10. Inembodiments of the present invention, the nose print of an animal, suchas a stray dog, can be used to uniquely identify the animal, much as afingerprint can be used to uniquely identify a human. Once a photographof the nose of pet 950 is taken, the nose print image of the pet can bestored locally in image database 907 via camera app 904.

As an alternative to a zoomed photograph of a stray pet's nose, inexemplary embodiments, an end user may use camera app 904 to insteadtake a zoomed photograph of the one or both of the stray pet's irises.As is the case for nose prints, the irises of an animal can uniquelyidentify a pet because it is nearly impossible for two different animalsto have the same iris pattern.

As described in connection with FIG. 9, Pet ID app 905 can be used by anend user to communicate, via link 960, to a remote server (such asremote server 1030) to obtain information relating to the nose print ofthe pet depicted in a stored photograph. Pet ID app 905 is configured totransmit, via wireless network adapter 906, one or more pet nose printphotographs over link 960, along with an associated data requestrelating to the nose prints in the transmitted photographs. Further, PetID app 905 is configured to receive a response to the data request anddisplay information received from remote server 1030. In embodiments,like pet ID app 105 in FIG. 1, pet ID app 905 may communicate over line960 using a Uniform Resource Locater (URL) for remote server 1030.

As shown in FIG. 9, system 1000 also includes remote server 1030. Inexemplary embodiments, remote server 1030 can be a desktop computer, alaptop computer, a tablet, a smartphone, or any server quality computer.Remote server 1030 is configured to communicate over a wide area orlocal area network. As shown, remote server 1030 communicates over link960. Link 960 is a communication link between remote server 1030 andmobile computing device 901. In embodiments, like remote server 930 inFIG. 1, remote server 1030 is configured to receive and respond torequests from mobile computing device 901. As shown in FIG. 9, remoteserver 1030 is operatively connected to database 1040.

According to exemplary embodiments, database 940 associates digitalphotographs of nose prints of pets with corresponding information. Inexemplary embodiments, database 1040 may be a relational database, ahierarchical database, or a structured text file. In embodiments,database 1040 is a centralized, globally accessible database that ispublic and non-proprietary. That is, database 1040 may be configured tobe queried separately from a device other than mobile device 901. Forexample, in embodiments, database 1040 can be configured to be accessed,updated, and queried through a web interface that is accessible to thepublic or to animal control authorities. In some embodiments, database1040 is configured to be deployed in a cloud computing environment. Inembodiments, database 1040 is independently accessible nationwide orworldwide using, for example, a mobile application used by emergencyresponse or law enforcement personnel, enabling quick and efficientidentification and rescue of lost pets. Database 1040, in someembodiments, can be accessed through a secure web interface. Further, inembodiments, link 960 may be a communication link over the Internet. Assuch, communication with remote server 1030 over link 960 can beestablished by pet ID app 905 using a URL that identifies remote server1030.

According to exemplary embodiments, remote server 1030 can receive arequest for information from mobile computing device 901. A request forinformation can include a zoomed digital photograph of the nose of astray pet. Upon receipt of the request and digital photograph, remoteserver 1030 invokes nose print recognition module 1035. Nose printrecognition module 1035 is a software module executed by remote server1030. Nose print recognition module 1035 is configured to read in adigital photograph of the nose or nose print of an animal, and to selectcertain nose print features of the photograph in accordance withtechniques known in the art. After analyzing and selecting nose printfeatures from the received photograph, nose print recognition module1035 accesses database 1040. Similar to database 940, database 1040stores images of the nose prints of previously registered pets andassociates those nose print images with information corresponding to thepet depicted in the image. Nose print recognition module 1035 comparesnose print features in the received photograph with nose print featuresin images stored in database 1040. If there is a match between the noseprint image in the received photograph and any of the nose print imagesin the database, then remote server 1030 retrieves informationassociated with the nose print image and transmits this information(such as pet photographs, medical information, and owner contactinformation) to mobile computing device 901 for display on display 902.

In exemplary embodiments, the nose print recognition module 1035 mayemploy pattern recognition algorithms such as, for example,classification methods, clustering methods, ensemble learningalgorithms, Bayesian networks, Markov random fields, multilinearsubspace learning algorithms, real-valued sequence labeling methods,regressions methods, sequence labeling methods and combinations thereof,to name a few.

FIG. 14 is a flowchart illustrating a nose print recognition algorithm,generally designated by reference number 1400, according to an exemplaryembodiment of the present invention. The nose print recognitionalgorithm 1400 includes steps of feature extraction 1401 andclassification 1403. In this exemplary embodiment, the nose printrecognition algorithm 1400 involves the use of a convolution neuralnetwork (CNN). CNN contains two basic operations, namely convolution andpooling. The feature extraction step 1401 employs a convolutionoperation, in which multiple filters are used to extract features(feature map) from the input data set, through which the extractedfeatures corresponding spatial information can be preserved. The poolingoperation, also called subsampling, is used to reduce the dimensionalityof feature maps from the convolution operation. After severalconvolutional and pooling layers, the classification step 1403 is donevia fully connected layers.

In some embodiments, remote server 1030 can be configured to registeriris images instead of, or in addition to, nose print images. In suchembodiments, database 1040 stores images of the irises of previouslyregistered pets and associates those iris images with informationcorresponding to the pet whose iris is depicted in a correspondingimage. It should be noted that the registration of irises might entailrequiring a visit to a veterinarian or other health professional whowould have an infrared camera necessary to acquire detail-rich andintricate structures of the iris. In such embodiments, remote server1035 may include an iris recognition module (not shown in FIG. 10) whichis configured to execute iris recognition software. Similar to noseprint recognition module 1035, the iris recognition module compares areceived iris image of a stray pet with registered images of pet irisesand transmits information pertaining to a registered pet if a match isfound.

FIG. 11 is a flow diagram of a method 1100 for a remote server toreceive requests for information associated with a photograph of a straypet, in accordance with exemplary embodiments of the present invention.Method 1100 is carried out, in exemplary embodiments, by a remoteserver, such as remote server 930 depicted in FIG. 9.

Method 1100 begins at step 1101. At step 1101, one or more facial imagesof pets are each associated with data associated with the correspondingpet in the image. In embodiments, such associated data can include: petowner information, pet health/medical information, one or moreadditional photographs of the pet, and the pet's home address. Otherinformation relating to the pet can be associated as well. Step 1101 canbe performed, in embodiments, in response to requests and interactionsby an end user or administrator with either local or remote access toremote server 930. Alternatively, the facial images and pet informationmay be associated by an end user of a mobile device transmitting afacial image and associated pet data from a mobile device, such asmobile device 901, using an app that is executing on the device, such asPet App 905. In such embodiments, remote server 930 receives the imagesand associated data along with a specified request from Pet App 905,such as “ASSOCIATE.”

Next, at step 1103, once one or more facial images have been associatedwith pet data, the facial images and pet data are then stored in adatabase, such as database 940. According to embodiments, the facialimages and associated pet data can be stored as records in a singletable or file or, alternatively, may be stored in several tables, eachhaving a unique pet identifier to tie the images and data together. Insuch embodiments, remote server 930 invokes facial recognition module935 to create a unique facial identifier to which the pet data is thenassociated. Remote server 930 then stores the unique facial identifierand associated pet data in database 940.

Next, at step 1105, remote server 930 monitors for and receives an imagefrom a user device, such as, for example, user device 901. As previouslymentioned, remote server 930 receives images over link 960.

At step 1107, remote server 930 retrieves registered facial images ofpets from database 940. In embodiments, the retrieved facial images havebeen pre-processed by facial recognition module 935 for easy comparisonby that module or other facial recognition software.

At step 1109, remote server 930 processes the received images and, ifnot pre-processed, the registered facial images using facial recognitionmodule 935, according to facial recognition techniques known in the art.At step 1111, remote server 930 determines whether the processedreceived images matches any one of the retrieved registered facialimages from database 940. If there is a match, method 1100 proceeds tostep 1113. If no match is found, then method 1100 proceeds to step 1117.

At step 1113, remote server 930 retrieves pet data associated with thematching registered facial image. In accordance with exemplaryembodiments, the associated pet data may include additional photographsof the pet, owner information for the pet, behavioral information forthe pet, and medical information for the pet.

Next, at step 1115, remote server 930 transmits the retrieved associatedpet data to the user device that sent the pet image. After step 1115,method 1100 returns to step 1105 to monitor for and receive an imagefrom a user device 160.

In the case where a match was not found, at step 1111, by facialrecognition module 935, method 1100 proceeds to step 1117. At step 1117,remote server 930 transmits a message to the user device 160 from whichthe server received the pet image that indicates that the petcorresponding to the received image was not found. After step 1117,method 1100 returns to step 1105 to monitor for and receive an imagefrom a user device 160.

FIG. 12 is a flow diagram of a method 1200 for a remote server toreceive requests for information associated with a photograph of a noseprint of a stray pet, in accordance with exemplary embodiments of thepresent invention. Method 1200 is carried out, in exemplary embodiments,by a remote server, such as remote server 930 depicted in FIG. 9.

Method 1200 begins at step 1201. At step 1201, one or more nose printimages of pets are each associated with data associated with the petthat corresponds to the respective nose print. In embodiments, suchassociated data can include: pet owner information, pet health/medicalinformation, one or more additional photographs of the pet, and thepet's home address. Other information relating to the pet can beassociated as well. Step 1201 can be performed, in embodiments, inresponse to requests and interactions by an end user or administratorwith either local or remote access to remote server 930. Alternatively,the nose print images and pet information may be associated by an enduser of a mobile device transmitting a nose print image and associatedpet data from a mobile device, such as mobile device 901, using an appthat is executing on the device, such as Pet App 905. In suchembodiments, remote server 930 receives the images and associated dataalong with a specified request from Pet App 905, such as “ASSOCIATE.”

Next, at step 1203, once one or more nose print images have beenassociated with pet data, the nose print images and pet data are thenstored in a database, such as database 940. According to embodiments,the nose print images and associated pet data can be stored as recordsin a single table or file or, alternatively, may be stored in severaltables, each having a unique pet identifier to tie the images and datatogether. In such embodiments, remote server 930 invokes nose printrecognition module 1035 in order to create a unique nose printidentifier to which the pet data is then associated. Remote server 930then stores the unique nose print identifier and associated pet data indatabase 940.

Next, at step 1205, remote server 930 monitors for and receives an imagefrom a user device, such as, for example, user device 901. As previouslymentioned, remote server 930 receives images over link 960.

At step 1207, remote server 930 retrieves registered nose print imagesof pets from database 940. In embodiments, the retrieved nose printimages have been pre-processed by nose print recognition module 1035 foreasy comparison by that module or other image recognition software.

At step 1209, remote server 930 processes the received images and, ifnot pre-processed, the registered nose print images using nose printrecognition module 1035, according to nose print recognition techniquesknown in the art. At step 1211, remote server 930 determines whether theprocessed received images matches any one of the retrieved registerednose print images from database 940. If there is a match, method 1200proceeds to step 1213. If no match is found, then method 1200 proceedsto step 1217.

At step 1213, remote server 930 retrieves pet data associated with thematching registered nose print image. In accordance with exemplaryembodiments, the associated pet data may include additional photographsof the pet, owner information for the pet, behavioral information forthe pet, and medical information for the pet.

Next, at step 1215, remote server 930 transmits the retrieved associatedpet data to the user device that sent the pet image. After step 1215,method 1200 returns to step 1205 to monitor for and receive an imagefrom a user device 160.

In the case where a match was not found, at step 1211, by nose printrecognition module 1035, method 1200 proceeds to step 1217. At step1217, remote server 930 transmits a message to the user device 160 fromwhich the server received the pet image that indicates that the petcorresponding to the received image was not found. After step 1217,method 1200 returns to step 1205 to monitor for and receive an imagefrom a user device 160.

Further, as an alternative to the use of nose print images, method 1200may be carried out, in embodiments, in a similar manner using irisrecognition software. In such embodiments, one or more iris images areregistered by remote server 930 and stored in database 1040. Theregistered iris images are compared to received images of irises ofstray pets and are analyzed for a match in in accordance with irisrecognition techniques.

FIG. 15 is a representative diagram of a pet tagging system, generallydesignated by reference number 1500, according to an exemplaryembodiment of the present invention. The pet tagging system 1500 mayinclude a plurality of temporary bands 1505-1-1505-n, with eachtemporary band 1505-1-1505-n holding a corresponding pet ID tag1510-1-1510-n. In exemplary embodiments, the pet ID tags 1510-1-1510-nmay have all the structure and functionality as pet ID tags 110,including, for example, a unique identifier and GPS. The temporary bands1510-1-1510-n are configured for attachment to unaccompanied animalsafter an emergency or some other incident. For example, the temporarybands 1510-1-1510-n may be made of elastic material for easy placementaround an animal's neck or other part of the animal's anatomy. A firstresponder may tag the animal (or its cage) with one of the temporarybands 1510-1-1510-n, and then use a mobile device to take a picture ortwo of the animal. The mobile device automatically identifies andrecords the exact location where the photographs are taken. The taggedand unaccompanied animal are then sent to a designated rescue location.The photographs along with information regarding the location where thepet may be compiled in a lost pet database, and the database may bepublished online for pet owners to search for their lost pets after anemergency or other incident. This lost pet database may have searchtools such as, for example, location where the pet may have been foundand identifying characteristics, such as breed, markings, color, etc.Upon discovery of a lost pet on the lost pet database, an owner maycontact the operator of the lost pet database. The operator may thenlocate the pet by cross-referencing the identified pet with the uniqueidentifier associated with the pet ID tag 1510-1-1510-n on the temporaryband 1510-1-1510-n worn by that pet. The unique identifier can then beused to locate the pet by accessing information on a remote server thathad been gathering information from the pet ID tag 1510-1-1510-n sincethe animal was first discovered after the emergency or other incident.

FIG. 16 is a block diagram that illustrates a system, generallydesignated by reference number 1600, in accordance with an exemplaryembodiment of the present invention. The system 1600 may include thesame components as the system 100 as previously described with referenceto FIG. 1, including a mobile computing device 101, a pet ID tag 110,and a remote server 100. The system 1600 may also incorporate microchiptransponders 1601-1-1601-n that are injectable into pets and otheranimals. The microchip transponders 1601-1-1601-n may be conventionalinjectable microchip transponders such as those available from AveryDennison Corporation, Glendale, Calif., USA. In exemplary embodiments,the microchip transponders 1601-1-1601-n may have unique identifiers,such as unique serial numbers or some other identifying information,that are the same as or correlated with the unique identifiersassociated with the pet ID tags 110 within the system 1600. Accordingly,the unique identifiers of the microchip transponders 1601-1-1601-n maybe used to cross-reference information from a pet registry databaselinked to the pet ID tags, such as the database 140. In exemplaryembodiments, the microchip transponders 1601-1-1601-n may be configuredfor one-way or two-communication with mobile computing device 101, petID tags 110, and/or remote server 100.

Now that embodiments of the present invention have been shown anddescribed in detail, various modifications and improvements thereon canbecome readily apparent to those skilled in the art. Accordingly, theexemplary embodiments of the present invention, as set forth above, areintended to be illustrative, not limiting. The spirit and scope of thepresent invention is to be construed broadly.

What is claimed is:
 1. A system for displaying, on a display operativelyconnected to a mobile device, information associated with a pet, thesystem comprising: (A) one or more databases having stored thereoninformation comprising: 1) one or more unique identifiers, where each ofthe one or more unique identifiers is associated with a correspondingone of one or more wireless communication devices configured to beaffixed to a corresponding one of one or more pets; 2) pet informationrelated to each of the one or more unique identifiers, the petinformation comprising one or more of the following: images of thecorresponding pet, contact information associated with the correspondingpet, environmental conditions associated with the corresponding pet,behavior of the corresponding pet, and medical history of thecorresponding pet; (B) one or more processors; and (C) a non-transitorycomputer readable memory operatively connected to the one or moreprocessors and having stored thereon machine-readable instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform a method comprising: receiving, by one of the oneor more wireless communication devices, via a near-field communicationlink, a first request from a mobile device; and sending, by the one ofthe one or more wireless communication devices to the mobile computingdevice, via the near-field communication link, a first response, thefirst response comprising the unique identifier associated with thewireless communication device, so the pet information associated withthe unique identifier may be accessed from the one or more databases fordisplay on the mobile computing device.
 2. The system of claim 1,wherein the first near-field communication link is a Bluetoothcommunication link.
 3. The system of claim 1, wherein the firstnear-field communication link is a WiFi communication link.
 4. Thesystem of claim 1, wherein the first near-field communication link is alink in a mesh communication network.
 5. The system of claim 1, whereineach of the one or more wireless communication devices comprises: ahousing; an antenna; a wireless transceiver operatively connected to theantenna; one or more near-field communication chips configured totransmit and receive electronic data via the wireless transceiver; and anon-transitory computer readable memory disposed within the housing. 6.The system of claim 5, wherein each of the one or more wirelesscommunication devices further comprise one or more sensor componentsconfigured to detect status of the wireless communication device.
 7. Thesystem of claim 6, wherein the one or more sensor components comprise:an accelerometer configured to measure an acceleration status of thewireless communication device; a global positioning module configured todetermine a geographic location status of the wireless communicationdevice; and a temperature sensor configured to determine an ambienttemperature status of the wireless communication device.
 8. The systemof claim 6, wherein the detected status is stored in the non-transitorycomputer-readable memory of the corresponding one or more wirelesscommunication devices.
 9. The system of claim 5, wherein the one or morewireless communication devices further comprise: a battery configured toprovide power to the wireless communication device; and a lightingelement configured to illuminate the wireless communication device. 10.The system of claim 8, further comprising a remote server.
 11. Thesystem of claim 10, wherein the method further comprises: receiving, bythe one of the one or more wireless communication devices, from theremote server, a second request; and sending, in response to the secondrequest, from the one of the one or more wireless communicationsdevices, to the remote server, the detected status of the one of the oneor more wireless communication devices, for storage in the one or moredatabases as associated with the corresponding unique identifier of theone of the one or more wireless communication devices.